Mapping Data Objects

The data objects in the source do not always exist in the destination or perhaps they use different naming conventions. These differences can be resolved by matching a data object in the source that does not exist in the destination to a different but comparable data object in the destination. This process is called mapping.

Overview

To ensure that the Source objects are transported to the correct Destination objects, Transporter provides a mapping mechanism. Mapping data is applied to an object's referenced objects and not to the actual object itself. Mappings automate the transporting process as discrepancies between source and destination object references are automatically mapped given the mapping rules. For convenience, mapping rules can be saved in a map file and restored later.

The mapping process is done in the Scheduler Object Mapping dialog. In this dialog, a list of the various types of data objects is divided into two columns. One column displays the data objects of the source and the other column displays the data objects of the destination Master. By comparing the source and destination side-by-side, you can easily spot any differences that need to be mapped.

The mapping process involves going down the column of source data objects and ensuring that a match for the comparable data object that is missing in the destination is mapped. Once the mapping is completed, the transporting process that transports the jobs or other data types from one source to another can start. Mapping can also be done dynamically for Job transports during the actual transporting procedure so that a complete map is built over time.